home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19981211-19990422
/
000115_news@watsun.cc.columbia.edu _Tue Jan 12 10:15:05 1999.msg
< prev
next >
Wrap
Internet Message Format
|
1999-04-21
|
2KB
Return-Path: <news@watsun.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA07156
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 12 Jan 1999 10:15:05 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id KAA00034
for kermit.misc@watsun.cc.columbia.edu; Tue, 12 Jan 1999 10:13:43 -0500 (EST)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Subject: Re: Help: Transmitting to Kermit TSO 4.3.2
Date: 12 Jan 1999 15:13:43 GMT
Organization: Columbia University
Message-ID: <77for7$o$1@newsmaster.cc.columbia.edu>
To: kermit.misc@mailrelay2.cc.columbia.edu
In article <369a9176.10188882@news.ozemail.com.au>,
<brad.de.groot@gecits-ap.com> wrote:
: I previously had Kermit TSO 4.0 and have upgraded to Kermit TSO
: 4.3.2. Now when I try to receive a file and type STAT, I obtain the
: following...
:
: Last file used: 'SUP.C738.P503.EQP01'
: Bytes/pkt: S=167 R=148 requiring 1 pkt
: Bytes/sec: S=33 R=30 requiring 5 sec
: Disk bytes/sec: 0 = 0% (SPEED 1200)
: 4 repeat packets sent
: Optimum packet size: 141
: Bad packet or chksum
:
: I was sending the file at a speed of 9600.
:
: Please note that I am relatively new to Kermit and unsure as to where
: to look in terms of setting up parameters to fix such an error. I'm
: not even sure if I have provided enough information here to obtain a
: proper response.
: So any help would be greatly appreciated.
:
Checksum errors can be caused by data corruption or data loss. This is
why we have checksums in the first place.
But in the IBM mainframe world, which uses parity, they can also be caused
by a parity mismatch. Make sure your client program is set to use the same
parity (even, mark, etc) that the mainframe (or its front end) expects.
- Frank